Method and system for coordinating device setting between a communications client and its host device

ABSTRACT

A system and method for propagating device settings to a data communications client from a host on a mobile device, the system having at least one host application adapted to operate on the mobile device host and further adapted to change device settings on the mobile device; a notification means adapted to notify the data communications client of device settings changes on the mobile device; a mode setting at the data communications client, the mode setting adapted to indicate whether client applications on the data communications client should use device settings from the host; and a client settings application adapted to receive a notification from the notification means and change device settings for the client applications if the mode setting indicates the client applications should use device settings from the host.

FIELD OF THE APPLICATION

The present application deals with the coordinating device settingbetween a data communications client and its host device, in particular,to the propagation of settings from the host to the data communicationsclient when a client mode is set to adopt the host settings.

BACKGROUND

In a host wireless device, it is sometimes desirable to add a clientonto the host to perform functionality that the host normally would notinclude. The host is typically certified with its software and hardwareto communicate over a wireless network, whereas a client typically wouldnot be. Further, certification could occur prior to the client beingadded, especially in the case that the client is integrated after-marketonto the wireless device.

It is further desirable that the client is able to communicate with thenative applications on the host and that the host applications are ableto communicate with client applications. This communication preferablyincludes controlling a user interface on the host device from a clientapplication, including registering inputs to the host device for theclient application and displaying or outputting from the clientapplication.

In some cases it is also desirable to be able to use device settingsfrom the host environment in a client setting. Examples of this couldinclude locale information, time zones, display themes, date format,time format or backgrounds. The automatic propagation of a change inhost device setting would be preferable in some situations.

In one embodiment it is also desirable to have symbol inputs to a clientcorrespond with symbol inputs to a host. It is further desirable thatthe input of symbols be simplified.

It is further desirable to be able to upgrade or downgrade theprovisioning of a client directly from a host device without having toload new software on the host device.

BRIEF DESCRIPTION OF THE DRAWINGS

The present system and method will be better understood with referenceto the drawings in which:

FIG. 1 is a schematic diagram of the components and dataflow accordingto the present system and method;

FIG. 2 is a screen-capture of a host application showing variousapplications that can be selected in the host environment;

FIG. 3 is a screen-capture of a client application started from a hostenvironment;

FIG. 4 is a screen-capture of a client application started from the hostenvironment in a host application;

FIG. 5 is a schematic diagram of the components and dataflow for a userinterface according to one aspect of the present system and method;

FIG. 6 is a view of a host symbol table;

FIG. 7 is a view of various input options on a host device;

FIG. 8 shows a 9*6 grid in a generally QWERTY keyboard layout withsymbols mapped to certain letters;

FIG. 9 shows a 9*6 grid in a generally AZERTY keyboard layout withsymbols mapped to certain letters;

FIG. 10 shows a 9*6 grid in a generally QWERTZ keyboard layout withsymbols mapped to certain letters;

FIG. 11 is a block diagram illustrating a host mobile station;

FIG. 12 is a flowchart showing the upgrade in the provisioning of aclient;

FIG. 13 is a flowchart showing the downgrade in the provisioning of aclient; and

FIG. 14 is a block diagram illustrating the propagation of changes inthe host environment to the data communications client.

DETAILED DESCRIPTION OF THE DRAWINGS

The present system and method provides a divided architecture forintegrating a client into a host wireless device. One key to the presentsystem is that the host is recognized as the dominant determinant in adivided architecture due to the fact that device type certificationefforts (Global Certification Forum (CGF)/PCS Type Certification ReviewBoard (PTCRB)) may happen prior to the client being integrated onto thehost. This necessitates that the host and tightly-tied applications tothe host remain unfettered.

The present system and method provides a virtual machine that is startedupon start-up of the host device and is used to run client applications.The virtual machine communicates through a client OS that would normallysend client application commands and functions to host dependentfeatures, such as hardware, software, firmware or communicationsnetworks. However, since the host dependent features are certified andcontrolled by the host device, the operating system instead communicateswith abstraction layers. The abstraction layers have a native interfacefor communicating with host applications, allowing client applicationsto use the host dependent features by utilizing host applications.

Device setting such as locale, time zone, display themes, date format,time format and backgrounds can be set using a binary variable. In onemode, the client settings are adapted to automatically adjust when hostdevice settings are changed. This change is propagated by either havinga listener at the host to signal a change in device settings, or pollingwhen a graphical interface of a client is brought to the foreground. Inthe other mode the client settings can be fixed at the client andchanges at the host device are ignored.

A client application accesses the user interface of a host device usinga host native application, a platform abstraction layer and a hostindependent engine communicating between the user interface and a clientapplication. The host independent engine is platform independent andrelies on the platform abstraction layer to translate and/or mapfunction calls. The host native application depends on the userinterface and host device, and is used to control actions and updates tothe user interface.

One example of an input for the host native application is the input ofsymbols. In a system for inputting symbols to a client where the hosthas a native system for inputting symbols from a host symbol table bynavigating a host cursor to move between adjacent symbols displayedwithin a host grid and the host further has a keyboard, the keyboard canbe taken advantage of to map symbols to one keystroke. A client symboltable is created conforming to the host symbol table, and a grid is madewhere the indicia of at least one keyboard key is associated with asymbol such that when a user actuates a key in the keyboard, the cursorjumps to the corresponding symbol.

Provisioning of the device can be accomplished from software that isalready loaded onto the device. By following steps from a clientapplication on a host device provisioning of the client can be changed.A host device user is thereby enabled to upgrade or downgrade clientservice, i.e. to provision the data client

The present application therefore provides a system for propagatingdevice settings to a data communications client from a host on a mobiledevice, said system comprising: at least one host application adapted tooperate on the mobile device host and further adapted to change devicesettings on the mobile device; a notification means adapted to notifythe data communications client of device settings changes on the mobiledevice; a mode setting at the data communications client, said modesetting adapted to indicate whether client applications on the datacommunications client should use device settings from said host; and aclient settings application adapted to receive a notification from thenotification means and change device settings for said clientapplications if said mode setting indicates said client applicationsshould use device settings from said host.

The present application further provides a method for propagating devicesettings to a data communications client from a host on a mobile device,said method comprising the steps of: changing device settings on themobile device using at least one host application; notifying the datacommunications client of device settings changes on the mobile device;checking a mode setting at the data communications client to determinewhether device settings changed at the host should be propagated to thedata communications client; and if the checking step determines changesshould be propagated, changing device settings for said datacommunications client.

The present system and method is directed to a divided architecture fora client on a host device. One example of such an arrangement would be adata-enabled cellular telephone with a data device client running on topof the host telephone environment. Other examples of clients running onhost environments would, however, be known to those skilled the art andthe above is not meant to limit the scope of the present method andsystem. The examples below will use a host that is a cellular telephoneand a client that is a data device client merely for illustrationpurposes.

A host device will require certification prior to being released forsale and use in a given market. Examples of certification include GSF-and PCS-type certification review board (PCTRB) certifications. Thesecertifications are for the hardware and tightly-tied applications tothis hardware.

In order to include a client that has communications capabilitieswithout having to certify the client, the integration of the clientrequires a divided architecture in which the phone and the tightly-tiedapplications to the phone remain unaltered.

One example of an architecture to accomplish this is illustrated inFIG. 1. FIG. 1 shows a method and system for a divided architecture 10which includes client applications 20 running on top of a virtualmachine 22.

Client applications 20 can be any application that is designed to run ona virtual machine 22. In the example of FIG. 1, these could include amessages application 31 for viewing messages that have been received, acontacts application 32, which presents an address book including phonenumbers, e-mail addresses or other contact information for individualsor companies, calendar application 33 for scheduling appointments andmanaging time, a browser application 34 for browsing the internet orother network, a compose-message application 35 to compose messages forSMS or e-mail, a save-messages application 36 to view messages that havebeen saved, a search-messages application 37 to search for a particularmessage, a lock application 38 to lock the keyboard and screen of themobile device, and a set-up application 39 to change the set-upconfiguration for client 15. Other applications 30 could also exist aspart of client applications 20 and the above-listed applications are notmeant to be limiting. Further, other clients besides client 15 couldexist on the host device and these other clients could have applications29 which could be invoked from application 30.

Virtual machine 22 is preferably started at power-up of the host deviceand stays running no matter what. In one preferred embodiment, thevirtual machine is a JAVA virtual machine and client applications 20 areJAVA applications.

All client applications 20 use virtual machine 22 to invoke instances ofobjects created by client applications 20.

A feature call such as a hardware call on system 10 from clientapplications 20 would normally go through client OS 24. Client OS 24includes a number of primitives for interacting with hardware. However,in the case that client applications 20 are built onto a host device andbecause the host device has acquired certification for its hostdependent features such as hardware, software and firmware, it ispreferable that instead of interacting with the features directly,client OS 24 interacts with a host abstraction layer 26. Hostabstraction layer 26 converts calls from client applications 20 to hostcalls through a native interface 28. Native interface 28 invokes hostapplications 40 in order to use the host dependent features on the hostdevice.

Because host applications invoke the features of the host device ratherthan client applications directly utilizing the features, the abovearchitecture provides that client applications 20 can run on a hostenvironment and use the features of the host device without having tore-certify. This enables the client to be added to the host device aftercertification, including an after-market addition to the host device.

One example of a client application using the above includes the makingof a telephone call when the host device is a cellular telephone. Whenin the host environment this simply involves using host applications tocreate the telephone call where these host applications use certifiedhardware, firmware and software to connect through the wireless system.However, when in a client application 20, the above architecturerequires the invoking of a host application in order to make the phonecall. A client application could be an address book or contactapplication 32 that includes phone numbers for individuals. A user maywish to select a phone number from the address book and have thewireless device phone that person. In order to accomplish this, a usermay select the phone number and select an option to phone that phonenumber. In this case, contact application 32 indicates through virtualmachine 22 to OS 24 that it needs to make a phone call. Instead of usingthe host dependent featrue directly from OS 24, a notification is sentto host abstraction layer 26 which, through native interface 28 invokesthe correct host application 40 to make the phone call. In the exampleof FIG. 1, this would be phone application 42. Phone application 42 thenstarts the phone call and the user proceeds as if the phone call wasstarted from client application 20.

Similarly, client application 20 could give a user the option (insteadof phoning the phone number) to use a short-message service or amulti-media message service to contact the individual. In each of thesecases, a different host application 40 is invoked, but this is donesimilarly through the host abstraction layer 26 and native interface 28.In the example of FIG. 1, these host applications include SMSapplication 44 or MMS application 46.

An alternative example of a client application 20 could be an e-mailmessage that includes a phone number within it, for example, in messagesapplication 31. Messages application 31 could give a user the option tocontact the phone number with the message. A phone-related application42, short-message service (SMS) application 44, or multi-media messageservice (MMS) application 46 is started within host applications 40.This is done through the client OS 24 to the host abstraction layer 26where the request is converted with a native interface 28 for a hostapplication 40.

As one skilled in the art will realize, data is supplied between theapplications 20 and host applications 40. In the example above, thephone number would be supplied to host application 40 including phoneapplication 42, SMS application 44, and MMS application 46.

It is further desirable that a client application can be activated froma host application 40. Reference is now made to FIG. 2. FIG. 2 shows ascreen capture of a host application. The host application lists aseries of client applications that can be activated. As used herein,activated can mean to both start a client application 20 or to bring analready started client application 20 to the foreground. In order toactivate a client application 20, the user scrolls to the clientapplication that s/he desires and selects the client application.Reference is made again to FIG. 1. When an application is selected inthe host environment, a client application selection application 48 usesa set of application programming interfaces (APIs) by which the hostoperating system can request a client application 20 to activate.

Client application selection application 48 uses a client abstractionlayer 50 to activate an application within client applications 20.Client application selection application 48 calls a function that istranslated in client abstraction layer 50. Client abstraction layer 50then uses virtual machine 22 to activate a client application 20.

Client abstraction layer 50 in alternative embodiments can either injectthe client OS 24 event into virtual machine 22 which causes the selectedclient application 20 to become active or, alternatively, performs a“reverse native call”, either through client OS 24 or via client connect52 to manipulate the native representation of some client object whichcauses the selected client application 20 to become active.

Client connect 52 can be used for network features for clientapplications. This enables, for example, client 15 to communicate usinga specific protocol that was not originally supported on the hostdevice. Client connect 52 involves a protocol stack to perform thismessaging, and thereby increase and improve client functionality.

An example of the above is a client calendar application as illustratedin the screen-capture FIG. 3, or a client e-mail application asillustrated in the screen-capture FIG. 4. Requests for a clientapplication to be activated are converted into function calls throughnative interface 28, which, in turn, makes calls on client applications20. These applications 20 are then brought into the display foreground.

FIG. 3 represents calendar application 33 and FIG. 4 represents ascreen-capture of the display of messages application 31. As will beappreciated by one skilled in the art, a screen bar or other marker onthe screen capture could be used to indicate that the client is in thehost environment.

Alternatively, client application selection application 48 maycommunicate directly with virtual machine 22 in order to activate aclient application 20. This may occur, for example, in the case whereclient application selection application 48 knows the code or a hook tostart client application 20.

Once virtual machine 22 receives a message to activate an application,either from the client application selection application 48 directly orthrough client abstraction layer 50, a client application is activatedand needs to assume control of the host user interface. In order to dothis, client application 20 makes a call back to client applicationselection application 48 indicating that client application 20 needs theuser interface. Client application selection application 48 then useshost code to take over the UI and thus becomes a portal between clientapplication 20 and the host. Client application selection application 48adapts all of the host inputs to events for the client and takes overcontrol of the user interface. Client application selection application48 is an uncertified embodiment of a host native application 60described in more detail below. As will be appreciated by one skilled inthe art, other embodiments could by certified.

If the host requires control of the user interface back, client 15 isnotified through client application selection application 48 of this.

It is further desirable when using a host and a client that the devicesettings be synchronized in certain situations. Device settings couldinclude locale settings, time zone settings, date format settings, timeformat settings or theme settings. Locale, as described herein, includesvarious settings such as the language of the interface, for example,English or French or Spanish. It could also include the keyboardconfiguration, e.g., QWERTY, AZERTY, QWERTZ or DVORAK. Theme settingscould include color patterns and background images.

In setup application 39 referred in FIG. 1, a user can choose between amode that allows the user to use host settings for the device settingsor custom settings. As one skilled in the art will appreciate, adifferent mode setting could be used for theme, locale and time zone, orthese could be all included in one mode setting.

If the mode is set to the host settings, the device settings for theclient are synchronized with the host's device settings. Any changes inthe host's device settings are propagated to the client and the client'sdevice settings are, therefore, also changed. For example, if a userchanges the language from French to English in a host application 40,this is propagated to client 15 and client applications 20 will useEnglish.

In the case where the client display is set to mimic the host display,propagation of changes in the host display is accomplished by having alistener application monitoring the host device settings. Upon a changein the host device settings, the host listener will notify setupapplication 39 that a change has been made to the host device settingsand this change will be reflected in the client device settings.

Alternatively, propagation of a change in the device settings couldinclude polling every time a graphical user interface from the clienttakes over. This polling involves comparing the host device settingswith the client device settings and thereby determining if a change hasbeen made. If a change has been made, the client device settings areupdated.

Thus if the mode is ‘automatic’ or ‘host settings’, changes in the hostdevice settings are pushed to the client, either through a listener orby polling, as described above.

If, conversely, the mode is set to ‘manual’ or ‘client settings’, theuser can update the device settings in the client and clientapplications will use these display setting instead of the host devicesettings. If the mode is set to ‘client settings’, changes to the host'sdevice settings will be ignored by client applications 20.

The above is better seen with reference to FIG. 14. A mobile device 1410includes a data communications client 1415 on a host communicationdevice having a certified portion 1440 for communications with thenetwork. Host device includes host applications 1442 which include adevice setting application 1443 allowing the user to change devicesettings. As described above, these settings can be various thingsincluding time zone settings, theme settings, locale, date formats, timeformats or other settings that the user may wish to have both on thehost and the client side. For example, the user may wish to use a24-hour format rather than a 12-hour format for time display and maychange this in device setting application 1443.

As will be appreciated, host applications run on a host operating system1444 and the host device includes storage 1446.

Once a user changes a device setting in device setting application 1443,this information is propagated to a device setting application 1424located on data communications client 1415. Device setting application1424 would then propagate the change to the applications 1420 that thechange affects. As will be appreciated by those skilled in the art, theupdate step from device setting application 1424 may be a global messagesent to all applications 1420 or may be sent to selected applications,for example through a registration means where applications indicate todevice setting application 1424 that they are interested in certainparameters. The change notification is sent through abstraction layer1428 and native interface 1426 as described above and applications 1420run on virtual machine 1424.

Device setting application 1424 may also access client storage 1430.

In one embodiment, the user has the option of telling the datacommunications client 1415 to ignore changes made on the hostenvironment. In this case, the user through settings user interfaceapplication 1422 indicates to the client that changes made on the hostenvironment should be ignored. In this case, device setting application1424 will first check with settings user interface application 1422 todetermine whether the change should be propagated to applications 1420.As will be appreciated by those skilled in the art, instead of devicesetting application 1424 checking with settings user interfaceapplication 1422, device settings application 1424 could check a flagwhich is persisted, preferably in non-volatile storage, and indicateswhether it should propagate the changes to applications 1420 and thisflag could be set based on settings user interface application 1422.

In order to propagate changes from host applications 1442, devicesetting application 1443 could send a message to device settingapplications 1424. This could be a periodic message or instigatedwhenever device setting applications 1443 is changed. Further, alistener 1448 could be employed to monitor when device settingapplication changes are made in which case they will notify devicesetting application 1424.

Based on the above, changes made in the host applications can bereflected in client applications in order to provide a user with aconsistent environment to operate in.

A further consideration for the above will be referred to herein asconflict resolution. In some instances, device settings that may be setin the host environment may not have an equivalent in datacommunications client 1415. For example, if the user sets the devicelanguage to Swahili in the host environment using device settingapplication 1443, this would get propagated to device settingapplication 1424. However, device setting application 1424 may not havea Swahili language setting for applications 1420. In this case, aconflict resolution scenario needs to be employed.

A first option for conflict resolution is an automatic mapping. In thiscase, the device will have a set of pre-programmed options that areavailable at the host which are not also available at the datacommunications client 1415. The list of exceptions further includealternatives that the data communications client 1415 should employshould the user select one of the non-supported options on the hostside. Thus, for example, if the user selects a language such as Swahilithat the data communications client 1415 does not support, devicesetting application 1424 may choose to proceed with English as thealternative language setting.

Alternatively, device setting application 1424 may prompt the user for adecision when an unsupported option is selected at the host side. Usingthe above example, if the user selects a language not supported by thedata communications client, device setting application 1424 may promptthe user for an alternative language for data communications client ormay ask whether the alternative that the device setting application haschosen is suitable.

As will be appreciated by those skilled in the art, exceptions willexist outside of language settings and may include, for example, timezone settings in certain parts of the world, unsupported theme settingsor other options known to those skilled in the art. The above is notmeant to be limiting and the present application could include all ofthese conflict situations, among others.

Reference is now made to FIG. 5. In order to interact with a user of ahost device, client applications 20 need to provide a user interface 90.On a host device having one or more input devices such as a keypad,keyboard, roller wheel, scrollstrip, touch-pad, d-pad or othernavigation device, and a screen, a user must be able to input actionsfor client applications 20, and the results of the input and clientapplications 20 operations need to be displayed on the screen. In orderto accomplish this, three components are provided within the I/Oarchitecture of the present system. These are a host-native application(HNA) 60, platform abstraction layer (PAL) 80, and a host-independentengine (HIE) 70.

HIE 70 is a platform independent component. Since PAL 80 contains thehost abstraction layer (HAL) 26 and the client abstraction layer (CAL)50, translation between the client and the particular host is performedin it. In a preferred embodiment PAL 80 is a C function interface.

HIE 70 includes both virtual machine 22 and client OS 24. These are usedto activate, start, or call instances of objects in client applications20 when client 15 is object oriented, or call functions in client 15when it is not.

HNA 60 resides beyond PAL 80, and thus can adapt user interface 90 toconform and adapt to a particular host on behalf of client applications20. HNA 60 can take radically different forms depending on the design ofthe host application infrastructure and the user interface requirementsof the host operating system. For example, it is envisaged that inalternate embodiments, a keyboard and display user interface arerequired, or alternatively a radically different voice-only interfacecan be provided. HNA 60 is responsible for creating the frameworknecessary to receive input and update output when a user brings a clientapplication 20 to the foreground. In a keyboard/display embodiment, thismay involve creating windows, buttons or graphics widgets of any kind.In a voice-only host embodiment, this may involve speech recognition andvoice synthesis.

For input 92, HNA 60 is responsible for passing user actions to HIE 70through platform abstraction layer 80. Inputs 92 can include buttonpresses, keystrokes, stylus inputs, roller wheel motions, scrollstripmotions, touch-pad motions, d-pad motions, voice commands, accelerometermotions or other inputs that would be known to those skilled in the art.These inputs are translated and/or mapped as received from the hostoperating system and fed through the input function of the platformabstraction layer 80.

For output 94, HNA 60 may receive screen updates from HIE 70 at anytime, including when client application 20 is not in the foreground.These updates must be stored and memory is used by HNA 60 to maintain acomplete frame buffer copy separate from the application display area.If HNA 60 is in the foreground when receiving an update from HIE 70,then the application display area must be updated as well as the framebuffer so that the display on the host device reflects the screen changeimmediately. Whenever HNA 60 transitions into the foreground, it mustupdate the application display area with the complete contents of theframe buffer.

Other output 94 types envisaged include audio tones, voice, and signalsto actuate host-specific features, such as an offset motor or led fordiscrete notification or indication.

In a preferred embodiment, HNA 60 uses a framework that updates the userby simply displaying a graphic image provided by PAL 80, and processesuser actions by adapting them to be sent down as events to PAL 80. Thisgreatly reduces the complexity of HNA 60 thus enhancing the portabilityof the client to other host devices.

Reference is now made to FIGS. 6-10 which illustrate a specific exampleof how HNA 60 adapts user actions and provides a user interface onbehalf of client applications adapted to the semantics of a particularhost.

First, a system for symbolic input on a particular host is shown in FIG.6. The system employs a particular semantic for symbolic input that theusers of traditional application on the host will expect to be valid onall applications utilized on the host.

Operationally, host graphical user interface element 100 offers a 9×6symbol table to a user. Cursor 102 is moved along a 9×4 grid in order toselect a symbol. Since the number of rows of the grid is smaller thanthat of the table, the symbols are offered on two pages,

Referring now to FIG. 7, the user may manipulate any number of inputdevices on a particular host, including a keypad 104, a 4-directionalD-pad 106, rocker switches 108, as well as a QWERTY keyboard provided intwo portions, a left keyboard portion 110L and a right keyboard portion110R. Most notably, the host semantics for symbolic input on thisparticular host require that cursor 102 be moved on the grid bymanipulating D-pad 106 to select a particular symbol.

In this particular example, HNA 60 preserves the semantics of symbolicinput on the host while adapting actions a client application user islikely to desire for symbolic input given the data-centric features ofclient applications 20.

Referring now to FIG. 8, operationally, client graphical user interfaceelement 114 offers a slightly different 9×6 symbol table on two pages,wherein symbols can still be selected by operation of d-pad 106, thuspreserving the host symbolic input semantics. Cursor 116 is now movedhowever on a 9×3 grid instead of a 9×6 grid. This grid height ispreferable in order to be able to map one row of each of the letter rowsof the keyboard of FIG. 7 to one of the symbol rows of the grid. Thewidth of the grid is maintained the same as in the host graphical userelement 114 to allow a traditional host application user to quicklylearn the layout of the symbol table while utilizing clientapplications, and to continue to contemporaneously support the use ofthe d-pad 106 for selecting a symbol.

Thus, a user is enabled to directly input one of 27 symbols using onekeystroke instead of having to resort to using the d-pad 106-D, whilestill accepting input using d-pad 106-D.

Note that the embodiments of FIGS. 8-10 deliberately do not use theright-most key of the top row of a standard keyboard, i.e. in the caseof the embodiment of FIG. 8, the key marked by the ‘P’ indicia in rightkeyboard portion 110R, since the topmost rows of the three standardkeyboards shown herein contains 10 keys. This has been shown above toprovide advantages and thus should not be considered a limitation.Nonetheless, it is envisaged that the techniques taught herein could beadapted to other keyboard layouts and grid sizes on a per host basis bythose of skill in the art, and thus those adaptations are also withinthe scope of this application.

In alternate embodiments, the unused keys can remain unutilized, or theycan be assigned a function to further enhance symbolic input, such astoggling between the various symbol pages. It is also envisaged thattoggling between symbol pages can be accomplished by use of any one ofthe many other keys available on the particular keyboard available onthe host keyboard.

FIGS. 9 and 10 illustrate how the HNA 60 can further adapt and conformto the semantics of variants of a host. In particular, FIG. 9 showsadaptation and conformity to a host variant having an AZERTY keyboard,and FIG. 10 shows the same in the case of a QWERTZ keyboard. Note thatin each case, the indicia used in user interface element 114 conforms tothe layout of the particular host keyboard, and that the input actionstaken by the user are adapted to select the corresponding symbol.

To summarize the example, for input, HNA 60 adapts keystrokes by mappingeach grid location on the 9×3 grid onto a key on the keyboard graphicaluser interface element, shown as QWERTY, AZERTY and QWERTZ variants inFIGS. 8,9 and 10 respectively. For output, HNA 60 enhances the displayby showing the indicia of a corresponding alphabetic key directly beloweach symbol.

Referring to the drawings, FIG. 11 is a block diagram illustrating ahost mobile station including preferred embodiments of the techniques ofthe present application. Mobile station 1100 is preferably a two-waywireless communication device having at least voice and datacommunication capabilities. Mobile station 1100 preferably has thecapability to communicate with other computer systems on the Internet.Depending on the exact functionality provided, the wireless device maybe referred to as a data messaging device, a two-way pager, a wirelesse-mail device, a cellular telephone with data messaging capabilities, awireless Internet appliance, or a data communication device, asexamples.

Where mobile station 1100 is enabled for two-way communication, it willincorporate a communication subsystem 1111, including both a receiver1112 and a transmitter 1114, as well as associated components such asone or more, preferably embedded or internal, antenna elements 1116 and1118, local oscillators (LOs) 1113, and a processing module such as adigital signal processor (DSP) 1120. As will be apparent to thoseskilled in the field of communications, the particular design of thecommunication subsystem 1111 will be dependent upon the communicationnetwork in which the device is intended to operate. For example, mobilestation 1100 may include a communication subsystem 1111 designed tooperate within the Mobitex™ mobile communication system, the DataTAC™mobile communication system, GPRS network, UMTS network, EDGE network orCDMA network.

Network access requirements will also vary depending upon the type ofnetwork 1119. For example, in the Mobitex and DataTAC networks, mobilestation 1100 is registered on the network using a unique identificationnumber associated with each mobile station. In UMTS and GPRS networks,and in some CDMA networks, however, network access is associated with asubscriber or user of mobile station 1100. A GPRS mobile stationtherefore requires a subscriber identity module (SIM) card in order tooperate on a GPRS network, and a RUIM in order to operate on some CDMAnetworks. Without a valid SIM/RUIM card, a GPRS/UMTS/CDMA mobile stationmay not be fully functional. Local or non-network communicationfunctions, as well as legally required functions (if any) such as “911”emergency calling, may be available, but mobile station 1100 will beunable to carry out any other functions involving communications overthe network 1100. The SIM/RUIM interface 1144 is normally similar to acard-slot into which a SIM/RUIM card can be inserted and ejected like adiskette or PCMCIA card. The SIM/RUIM card can have approximately 64K ofmemory and hold many key configuration 1151, and other information 1153such as identification, and subscriber related information.

When required network registration or activation procedures have beencompleted, mobile station 1100 may send and receive communicationsignals over the network 1119. Signals received by antenna 1116 throughcommunication network 1119 are input to receiver 1112, which may performsuch common receiver functions as signal amplification, frequency downconversion, filtering, channel selection and the like, and in theexample system shown in FIG. 11, analog to digital (A/D) conversion. A/Dconversion of a received signal allows more complex communicationfunctions such as demodulation and decoding to be performed in the DSP1120. In a similar manner, signals to be transmitted are processed,including modulation and encoding for example, by DSP 1120 and input totransmitter 1114 for digital to analog conversion, frequency upconversion, filtering, amplification and transmission over thecommunication network 1119 via antenna 1118. DSP 1120 not only processescommunication signals, but also provides for receiver and transmittercontrol. For example, the gains applied to communication signals inreceiver 1112 and transmitter 1114 may be adaptively controlled throughautomatic gain control algorithms implemented in DSP 1120.

Network 1119 may further communicate with multiple systems (not shown).For example, network 1119 may communicate with both an enterprise systemand a web client system in order to accommodate various clients withvarious service levels.

Mobile station 1100 preferably includes a microprocessor 1138 whichcontrols the overall operation of the device. Communication functions,including at least data and voice communications, are performed throughcommunication subsystem 1111. Microprocessor 1138 also interacts withfurther device subsystems such as the display 1122, flash memory 1124,random access memory (RAM) 1126, auxiliary input/output (I/O) subsystems1128, serial port 1130, keyboard 1132, speaker 1134, microphone 1136, ashort-range communications subsystem 1140 and any other devicesubsystems generally designated as 1142.

Some of the subsystems shown in FIG. 11 perform communication-relatedfunctions, whereas other subsystems may provide “resident” or on-devicefunctions. Notably, some subsystems, such as keyboard 1132 and display1122, for example, may be used for both communication-related functions,such as entering a text message for transmission over a communicationnetwork, and device-resident functions such as a calculator or tasklist.

Operating system software used by the microprocessor 1138 is preferablystored in a persistent store such as flash memory 1124, which mayinstead be a read-only memory (ROM) or similar storage element (notshown). Those skilled in the art will appreciate that the operatingsystem, specific device applications, or parts thereof, may betemporarily loaded into a volatile memory such as RAM 1126. Receivedcommunication signals may also be stored in RAM 1126.

As shown, flash memory 1124 can be segregated into different areas forboth computer programs 1158 and program data storage 1150, 1152, 1154and 1156. These different storage types indicate that each program canallocate a portion of flash memory 1124 for their own data storagerequirements. Microprocessor 1138, in addition to its operating systemfunctions, preferably enables execution of software applications on themobile station. A predetermined set of applications that control basicoperations, including at least data and voice communication applicationsfor example, will normally be installed on mobile station 1100 duringmanufacturing. A preferred software application may be a personalinformation manager (PIM) application having the ability to organize andmanage data items relating to the user of the mobile station such as,but not limited to, e-mail, calendar events, voice mails, appointments,and task items. Naturally, one or more memory stores would be availableon the mobile station to facilitate storage of PIM data items. Such PIMapplication would preferably have the ability to send and receive dataitems, via the wireless network 1119. In a preferred embodiment, the PIMdata items are seamlessly integrated, synchronized and updated, via thewireless network 1119, with the mobile station user's corresponding dataitems stored or associated with a host computer system. Furtherapplications may also be loaded onto the mobile station 1100 through thenetwork 1119, an auxiliary I/O subsystem 1128, serial port 1130,short-range communications subsystem 1140 or any other suitablesubsystem 1142, and installed by a user in the RAM 1126 or preferably anon-volatile store (not shown) for execution by the microprocessor 1138.Such flexibility in application installation increases the functionalityof the device and may provide enhanced on-device functions,communication-related functions, or both. For example, securecommunication applications may enable electronic commerce functions andother such financial transactions to be performed using the mobilestation 1100.

In a data communication mode, a received signal such as a text messageor web page download will be processed by the communication subsystem1111 and input to the microprocessor 1138, which preferably furtherprocesses the received signal for output to the display 1122, oralternatively to an auxiliary I/O device 1128. A user of mobile station1100 may also compose data items such as email messages for example,using the keyboard 1132, which is preferably a complete alphanumerickeyboard or telephone-type keypad, in conjunction with the display 1122and possibly an auxiliary I/O device 1128. Such composed items may thenbe transmitted over a communication network through the communicationsubsystem 1111.

For voice communications, overall operation of mobile station 1100 issimilar, except that received signals would preferably be output to aspeaker 1134 and signals for transmission would be generated by amicrophone 1136. Alternative voice or audio I/O subsystems, such as avoice message recording subsystem, may also be implemented on mobilestation 1100. Although voice or audio signal output is preferablyaccomplished primarily through the speaker 1134, display 1122 may alsobe used to provide an indication of the identity of a calling party, theduration of a voice call, or other voice call related information forexample.

Serial port 1130 in FIG. 11 would normally be implemented in a personaldigital assistant (PDA)-type mobile station for which synchronizationwith a user's desktop computer (not shown) may be desirable, but is anoptional device component. Such a port 1130 would enable a user to setpreferences through an external device or software application and wouldextend the capabilities of mobile station 1100 by providing forinformation or software downloads to mobile station 1100 other thanthrough a wireless communication network. The alternate download pathmay for example be used to load an encryption key onto the devicethrough a direct and thus reliable and trusted connection to therebyenable secure device communication.

Other communications subsystems 1140, such as a short-rangecommunications subsystem, is a further optional component which mayprovide for communication between mobile station 1100 and differentsystems or devices, which need not necessarily be similar devices. Forexample, the subsystem 1140 may include an infrared device andassociated circuits and components or a Bluetooth™ communication moduleto provide for communication with similarly enabled systems and devices.

A mobile communications device, such as a phone, is typically formed ofsoftware, firmware, and hardware adapted to provide communicationsservices over a wireless communications network. This process of formingthe relationship between the mobile communications device and theservice is known in the art as provisioning. Typically a networkoperator provisions the mobile via a subscription to a service contract.Thus, once the mobile has been provisioned, the user of the mobile isoften referred to as a subscriber.

In a voice and data network such as GSM (Global System for MobileCommunication) and GPRS (General Packet Radio System), CDMA (CodeDivision Multiple Access), or various other third generation networkssuch as EDGE (Enhanced Data rates for GSM Evolution) or UMTS (UniversalMobile Telecommunications Systems), both voice and data services may beavailable to mobile communications devices. Example voice servicesinclude voice calling and Short Messaging Service (SMS). Example dataservices include Internet browsing, email, and Multimedia MessagingService (MMS).

Although many services may be available on a given network, only thosesubscribers that use mobile communications devices that have beenprovisioned for those services will be able to benefit from them. Thismay present problems for the subscriber and the network operator alike.On one hand, the subscriber may desire an existing service he does nothave, i.e. an upgrade, or desire disabling a service, i.e. a downgrade.On the other hand the operator may want to offer a new service, but mayhesitate if subscribers cannot benefit from them.

One known solution is to provide an out of band communications link,such as a Universal Serial Bus, on the mobile communications device, andenable the subscriber to load new software onto the mobile via the outof band communication link using a personal computer, thusre-provisioning the device. This may be an unacceptable solution to boththe subscriber and the operator as there is a significant risk that themobile, by error, receives a wrong or incomplete load, and may requireservicing. Furthermore, this solution may be unacceptable to thesubscriber who does not have access to a personal computer.

However, since mobile station 1100 is a host communications device thathosts client 15, client 15 may be provisioned directly by a user ofmobile station 1110.

Referring now to FIG. 12, an exemplary upgrade of client 15 isillustrated.

Method of: User upgrade to UPGRADED client service

Pre-Condition(s): Device is configured to allow service change

Current Service Type=BASE Service Lock =NO_LOCK Service Change=NO_CHANGE

Acts and steps: 1 USER activates service configuration menu item.

-   -   2. CLIENT examines factory settings for service type 3. CLIENT        displays “Contact Operator” informational dialog to indicate to        the user that they must do this in order to get service.        (Display 1203)    -   4. USER selects to proceed. 5. CLIENT displays “Verification”        informational dialog to indicate user desires to upgrade and        indicates the need to reinstall desktop. (Display 1204)    -   6. USER selects to proceed. 7. CLIENT displays “Loss of Data”        question to verify the user has done a backup prior performing        upgrade. (Display 1205)    -   8. USER selects to proceed. 9. CLIENT saves new service type and        sets ‘service change’ flag.    -   10. CLIENT informs Host applications of required change to point        to Client applications    -   11. CLIENT triggers clear of Host calendar data. (Display 1206)    -   12. CLIENT informs user the device will be powered off. (Display        1207)    -   13. CLIENT requests Host to power off the device.    -   14. USER starts device.    -   15. HOST processes the change and clears ‘service change’ flag.    -   16. USER de-installs current Client desktop to remove base        configured desktop    -   17. User re-installs Client desktop and selects Upgrade        configuration.    -   18. USER connects device to Client desktop    -   19. Client Desktop synchronizes with wireless data server    -   20. Client Desktop associates identifier with user's corporate        email account    -   21. Client Desktop downloads keys & service books    -   22. Client Desktop performs bulk download of calendar    -   23. CLIENT registers on network    -   24. USER starts receiving wireless email and calendar events.

Post Provisioning recorded as complete.

Condition(s): Current Service Type=UPGRADED

-   -   Service Lock =NO_LOCK    -   Service Change =NO_CHANGE

Referring now to FIG. 13, an exemplary downgrade of client 15 isillustrated.

User wants to downgrade to base service

Method of: user downgrade to base service

Pre-Condition(s): Device is configured to allow service change

-   -   Current Service Type=BASE    -   Service Lock =NO_LOCK    -   Service Change =NO_CHANGE

Acts and steps: 1. USER activates service configuration menu item.

-   -   2. CLIENT examines factory settings for service type.    -   3. CLIENT displays “Verification” informational dialog to        indicate user desires to downgrade. (Display 1303)    -   4. USER selects to proceed.    -   5. CLIENT displays “Loss of Data” question to verify the user        has done a backup prior performing upgrade. (Display 1304)    -   6. USER selects to proceed.    -   7. CLIENT saves current service type    -   8. CLIENT informs Host applications of required change to point        to Host applications    -   9. CLIENT performs delete of all data contained in the CLIENT        file system    -   10. CLIENT informs Host applications to perform “KillDevice” IT        policy request to clear all corporate data in Host file systems.        (Display 1305)    -   11. CLIENT sets the ‘service change’ flag.    -   12. CLIENT informs user the device will be powered off. (Display        1306)    -   13. CLIENT requests Host to power off the device.    -   14. USER starts device.    -   15. HOST processes the change and clears ‘service change’ flag.    -   16. USER de-installs current Client desktop to remove upgrade        configured desktop    -   17. User re-installs Client desktop and selects base        configuration.

Post Provisioning recorded as complete.

Condition(s): Current Service Type=BASE

-   -   Service Lock =NO_LOCK    -   Service Change =NO_CHANGE

Thus, the host device user is enabled to upgrade or downgrade clientservice, i.e. to provision the data client.

The embodiments described herein are examples of structures, systems ormethods having elements corresponding to elements of the techniques ofthis application. This written description may enable those skilled inthe art to make and use embodiments having alternative elements thatlikewise correspond to the elements of the techniques of thisapplication. The intended scope of the techniques of this applicationthus includes other structures, systems or methods that do not differfrom the techniques of this application as described herein, and furtherincludes other structures, systems or methods with insubstantialdifferences from the techniques of this application as described herein.

1. A system for propagating device settings to a data communicationsclient from a host on a mobile device, said system comprising: at leastone host application adapted to operate on the mobile device host andfurther adapted to change device settings on the mobile device; anotification means adapted to notify the data communications client ofdevice settings changes on the mobile device; a mode setting at the datacommunications client, said mode setting adapted to indicate whetherclient applications on the data communications client should use devicesettings from said host; and a client settings application adapted toreceive a notification from the notification means and change devicesettings for said client applications if said mode setting indicatessaid client applications should use device settings from said host. 2.The system of claim 1, wherein the notification means includes alistener at said host, said listener adapted to monitor said hostapplications for device settings changes.
 3. The system of claim 2,wherein said listener is further adapted to notify the client settingsapplication.
 4. The system of claim 1, wherein the notification meansincludes a polling application located at said data communicationsclient, said polling application adapted to poll said at least one hostapplication to determine whether a device settings change has been made.5. The system of claim 4, further comprising a graphical user interfacemonitor adapted to determine when a client application has taken controlof a graphical user interface on the mobile device.
 6. The system ofclaim 5, wherein said polling application polls said at least one hostapplication when said graphical user interface monitor determines thatthe client application has taken control of the graphical user interfaceon the mobile device.
 7. The system of claim 1, further comprising anabstraction layer and a native interface layer between said at least onehost application and said client settings application, said abstractionlayer and native interface layer adapted for a particular host, allowingsaid data communications client to communicate with the particular host.8. The system of claim 1, wherein the mode setting is a flag that ispersisted.
 9. The system of claim 1, further comprising a conflictresolution application, said conflict resolution application adapted toprovide an alternative supported setting if said data communicationsclient does not support a setting set at said at least one hostapplication.
 10. The system of claim 9, wherein said conflict resolutionapplication includes a mapping table to map unsupported settings withthe alternative supported setting.
 11. The system of claim 9, whereinthe conflict resolution application includes a prompt for prompting auser to select the alternative supported setting.
 12. A method forpropagating device settings to a data communications client from a hoston a mobile device, said method comprising the steps of: changing devicesettings on the mobile device using at least one host application;notifying the data communications client of device settings changes onthe mobile device; checking a mode setting at the data communicationsclient to determine whether device settings changed at the host shouldbe propagated to the data communications client; and if the checkingstep determines changes should be propagated, changing device settingsfor said data communications client.
 13. The method of claim 12, whereinthe notifying step includes listening for changes at said host, saidlistening step monitoring said host applications for device settingschanges.
 14. The method of claim 13, wherein said notifying stepnotifies the data communications client when said listening step findsdevice settings changes have occurred.
 15. The method of claim 12,wherein the notifying step polls from said data communications clientsaid at least one host application to determine whether a change indevice settings has occurred.
 16. The method of claim 15, wherein saidpolling step is activated when a client application has taken control ofa graphical user interface on the mobile device.
 17. The method of claim12, further comprising a translating step, the translating stepoccurring in and abstraction layer and a native interface layer betweensaid host and the data communications client, said translating stepallowing a particular host to communicate with the data communicationsclient.
 18. The method of claim 12, wherein the checking step checks aflag at a preset memory location.
 19. The method of claim 12, furthercomprising the step of resolving conflicts before said changing step,said resolving conflicts step providing an alternative supported settingto said data communications client if said data communications clientdoes not support a setting set in said changing step.
 20. The method ofclaim 19, wherein said conflict resolving step chooses the alternativesupported setting from a mapping table that maps unsupported settingswith the alternative supported setting.
 21. The method of claim 19,wherein the conflict resolving step prompts a user to select thealternative supported setting.